feat: add support for dedicated_for parameter in update_access_key #723
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
cloudinary-pkoniu
requested changes
Nov 21, 2025
Contributor
Author
|
Hi @cloudinary-pkoniu, all requested updates are in, and the review comments are resolved. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Brief Summary of Changes
What Does This PR Address?
Are Tests Included?
Reviewer, Please Note:
When I hard coded the config and ran the provisioning tests locally, I got 6 passing tests and 17 pending. The pending ones relate to user provisioning and seem unrelated to the dedicated_for feature.
I removed the temporary config before committing, so the PR only includes the intended changes.